Compare Page

Format consistency

Characteristic Name: Format consistency
Dimension: Consistency
Description: Data formats are consistently used
Granularity: Element
Implementation Type: Rule-based approach
Characteristic Type: Declarative

Verification Metric:

The number of inconsistent data formats reported in an attribute per thousand records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Maintain consistent formats for data values across different data bases and different tables in the same database. (1) Telephone number :
Country code/Area code/number
(2) Address : House number, Street, Suburb, Sate, Country
Maintain structural similarity or compatibility of entities and attributes across systems (databases/data sets) and across time. (1) Customer record has the same structure in all systems which it is being used.
Maintain consistent and compatible encoding /decoding standards across different applications. (1) ASCII, UTF-8, XML

Validation Metric:

How mature is the creation and implementation of the DQ rules to maintain format consistency

These are examples of how the characteristic might occur in a database.

Example: Source:
1) Each class in a UK secondary school is allocated a class identifier; this consists of the 3 initials of the teacher plus a two digit year group number of the class. It is declared as AAA99 (3 Alpha characters and two numeric characters).

2) A new year 9 teacher, Sally Hearn (without a middle name) is appointed therefore there are only two initials. A decision must be made as to how to represent two initials or the rule will fail and the database will reject the class identifier of “SH09”. It is decided that an additional character “Z” will be added to pad the letters to 3: “SZH09”, however this could break the accuracy rule. A better solution would be to amend the database to accept 2 or 3 initials and 1 or 2 numbers.

3) In this scenario, the parent, a US Citizen, applying to a European school completes the Date of Birth (D.O.B) on the application form in the US date format, MM/DD/YYYY rather than the European DD/MM/YYYY format, causing the representation of days and months to be reversed.

N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.
if a data element is used to store the color of a person’s eyes, a value of TRUCK is invalid. A value of BROWN for my eye color would be valid but inaccurate, in that my real eye color is blue. J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
A measure of the equivalence of information stored or used in various data stores, applications, and systems, and the processes for making data equivalent D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
The extent to which similar attributes or elements of an information object are consistently represented using the same structure, format, and precision. STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.

 

Completeness of records

Characteristic Name: Completeness of records
Dimension: Completeness
Description: Every real world entity instance, that is relevant for the organization can be found in the data
Granularity: Record
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to missing records
The number of complaints received due to missing records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Implement a process level validation mechanism to avoid occurrence of missing records (1) A buyer must record/verify an expense or asset in accordance with accepting/receiving any purchased items. (2)New application are stored in a temporary cabinet after entering into the system and they will be transferred to the file cabinet at the end of every week after the property manager cross check them with the system
Execute database commits upon transaction sequences in application programs and make sure all the transactions in the sequence successfully commit and generate the required records at the end of the sequence. (1) In generating the MRP, the database operations will not be committed unless all materials in BOM is successfully executed for MRP
When distributed databases are used or online data collection devices are used, ensure the synchronisation/replication of records happen successfully without distortions and omissions. (1) EFTPOS transactions are replicated with bank database and create the new balance B/F in the account
Implement periodic audit process for critical tangible objects that are recorded as data in database (1) Annual audit for tangible assets in the organisation
Implement a validation mechanism in data transfers considering the business rules to monitor and ensure all records relevant to a event/transaction is transferred successfully. (1) Rules to verify the number of records in the source file and destination file (2) All records relevant to a customer trip is transferred to the central database from online data stores
Maintain error logs for system transactions and regularly monitor them and perform relevant forensic activities to find missing records. (1) A failed sales order creation

Validation Metric:

How mature is the process to prevent missing records

These are examples of how the characteristic might occur in a database.

Example: Source:
if Dept is a relation representing the employees of a given department, and one specific employee of the department is not represented as a tuple of Dept, then the tuple corresponding to the missing employee is in ref(Dept),and ref(Dept) differs from Dept in exactly that tuple. C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006.
if a column should contain at least one occurrence of all 50 states, but the column contains only 43 states, then the population is incomplete. Y. Lee, et al., “Journey to Data Quality”, Massachusetts Institute of Technology, 2006.
the database should contain all customers in North and South America, but it is known that the database reflects only a portion of the company’s customers. Coverage in this example is the percent- age of customers actually captured in the database compared to the population of all customers that should be in it. D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
A record exists for every Real-World Object or Event the Enterprise needs to know about. ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Completeness of data refers to the extent to which the data collected matches the data set that was developed to describe a specific entity. Monitoring for incomplete lists of eligible records or missing data items will identify data quality problems. HIQA 2011. International Review of Data Quality Health Information and Quality Authority (HIQA), Ireland. http://www.hiqa.ie/press-release/2011-04-28-international-review-data-quality.
Quality of having all data that existed in the possession of the sender at time the data message was created. ISO 2012. ISO 8000-2 Data Quality-Part 2-Vocabulary. ISO.
Data is complete if no piece of information is missing – anti-example: "The Beatles were John Lennon, George Harrison and Ringo Starr" KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published.
Every real-world phenomenon is represented. PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a.